CVE-2022-49897
Linux Kernel fscrypt Keyring Memory Leak Vulnerability
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
INFO
Published Date :
May 1, 2025, 3:16 p.m.
Last Modified :
May 8, 2025, 11:15 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Consult the CNA for more information.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-49897 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-49897 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 08, 2025
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 08, 2025
Action Type Old Value New Value Changed Description In the Linux kernel, the following vulnerability has been resolved: fscrypt: fix keyring memory leak on mount failure Commit d7e7b9af104c ("fscrypt: stop using keyrings subsystem for fscrypt_master_key") moved the keyring destruction from __put_super() to generic_shutdown_super() so that the filesystem's block device(s) are still available. Unfortunately, this causes a memory leak in the case where a mount is attempted with the test_dummy_encryption mount option, but the mount fails after the option has already been processed. To fix this, attempt the keyring destruction in both places. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Removed Reference kernel.org: https://git.kernel.org/stable/c/0b1747653b102c555bac745ebe5ca86cdd20e43f Removed Reference kernel.org: https://git.kernel.org/stable/c/29997a6fa60de1de2fa0de471e7652efa6e95868 Removed Reference kernel.org: https://git.kernel.org/stable/c/ccd30a476f8e864732de220bd50e6f372f5ebcab Removed Reference kernel.org: https://git.kernel.org/stable/c/cff805b1518f38d57866065343db2285f2dcd5ab -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 01, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: fscrypt: fix keyring memory leak on mount failure Commit d7e7b9af104c ("fscrypt: stop using keyrings subsystem for fscrypt_master_key") moved the keyring destruction from __put_super() to generic_shutdown_super() so that the filesystem's block device(s) are still available. Unfortunately, this causes a memory leak in the case where a mount is attempted with the test_dummy_encryption mount option, but the mount fails after the option has already been processed. To fix this, attempt the keyring destruction in both places. Added Reference https://git.kernel.org/stable/c/0b1747653b102c555bac745ebe5ca86cdd20e43f Added Reference https://git.kernel.org/stable/c/29997a6fa60de1de2fa0de471e7652efa6e95868 Added Reference https://git.kernel.org/stable/c/ccd30a476f8e864732de220bd50e6f372f5ebcab Added Reference https://git.kernel.org/stable/c/cff805b1518f38d57866065343db2285f2dcd5ab